[AAASM-2104] 🔧 (release): Bump python-sdk to 0.0.1a2 + refresh release intent#67
Conversation
Continue the cross-repo pre-release dry-run series. PEP 440
pre-release identifier (`0.0.1a2`) corresponds to SemVer
`v0.0.1-alpha.2`; the git tag mirrors the SemVer form.
Changes:
* pyproject.toml — version 0.0.1a1 → 0.0.1a2
* agent_assembly/__init__.py — __version__ 0.0.1a1 → 0.0.1a2
* uv.lock — regenerated by `uv lock`
* .github/tag_and_release/release-title.md — was placeholder
"v0.0.0 - Sample release note title 🍻" from the initial commit;
set to proper alpha-2 title
* .github/tag_and_release/release-notes.md — was placeholder
template content from the initial commit; replaced with actual
alpha-2 release notes covering the AAASM-2053 workflow-trigger
fix that landed since alpha-1
Verified:
* uv sync --locked → exit 0
* .venv/bin/python -m pytest test/ → 418 passed, 11 skipped
* .venv/bin/ruff check . → clean
* .venv/bin/mypy agent_assembly → clean
Tracked: AAASM-2104
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
|
Claude Code review — AAASM-2104CI state30 SUCCESS + 10 SKIPPED, 0 failures —
All 30 SUCCESS checks include the full pytest matrix (3.13 × ubuntu/ubuntu-22.04/macos/macos-14, both unit + integration), Scope vs. acceptance criteria
Why the release-intent refresh mattersThis PR fills a real gap: the alpha-1 release fired the release pipeline but the resulting GitHub Release body was meaningless because VerdictReady for human approval and merge. All CI green by-design (the 10 skipped jobs are correct, not failures). The release-intent refresh is the load-bearing change the user explicitly called out as required before tagging. — Claude Code (Opus 4.7, 1M context) |
1 participant
Description
Bump
python-sdkfrom0.0.1a1→0.0.1a2(PEP 440 form; the git tag will mirror asv0.0.1-alpha.2) for the cross-repo alpha-2 pre-release dry-run. Also refresh.github/tag_and_release/release-title.mdandrelease-notes.mdwhich were still at placeholder template content from the initial commit (cf0aa6b).Diff
pyproject.toml— version0.0.1a1→0.0.1a2agent_assembly/__init__.py—__version__0.0.1a1→0.0.1a2uv.lock— regenerated byuv lock.github/tag_and_release/release-title.md— was"v0.0.0 - Sample release note title 🍻", replaced with proper alpha-2 title.github/tag_and_release/release-notes.md— was template placeholder ("Newborn of something project..."), replaced with real alpha-2 content covering the AAASM-2053 workflow-trigger fix landed since alpha-1.github/tag_and_release/intent.yaml— no edit; PR [AAASM-2053] 🐛 (ci): Fix python-sdk workflow triggers + slack_mcp template leakage #66 already setartifacts.docs: skipcorrectlyWhy the intent config update
User flagged that the release workflow consults
.github/tag_and_release/release-title.md+release-notes.mdto compose the published GitHub Release. At alpha-1 these were still the initial-commit placeholders ("Sample release note title 🍻", "Newborn of something project") — the alpha-1 tag still fired the release pipeline but the resulting GitHub Release body was meaningless. This PR makes them load-bearing for alpha-2.Type of Change
Breaking Changes
Related Issues
Testing
uv sync --locked— exit 0.venv/bin/python -m pytest test/— 418 passed, 11 skipped (env-gated integration tests).venv/bin/ruff check agent_assembly/__init__.py— clean (pre-existing 189 ruff errors on master are unrelated to this PR; verified by stash + recheck)agent_assembly._coreimport-not-found is a maturin-build-time issue, not introduced by this PRChecklist
— Claude Code (Opus 4.7, 1M context)